Activity: Create Project Success Plan section 2 |
|
 |
Update and refine the project success plan |
|
Purpose
-
Create the Project Success Plan, which provides a
definition of what will enable this project to deliver a successful solution to the business. It is not a legally
binding contract or document. It constitutes a definition of why the project is being conducted, how the project
will deliver a result, and what criteria will determine if a successful outcome is achieved.
-
The Project Success Plan describes the project in
sufficient detail to:
-
Provide a common understanding of the project
vision and plans amongst all stakeholders.
-
Facilitate agreement on the project plans and
enable initiation of the solution design.
-
Provide a milestone plan and associated estimates
for the project design, configure, deployment and ongoing operation of the solution.
-
The components of section 2 of the plan
are:
-
Create exception statement
-
Create pre-configure and deployment
requirements
-
Create configure and deployment
assumptions
-
Create detailed configure and deployment
resource plan
-
Create detailed configure and deployment
schedule
-
Create appendices section 2.
|
Relationships
Usage
Usage Guidance |
Process Steps
-
Take the Project Success Plan Section 1 and use the Project Success Plan (Refined) template.
-
Complete Exception Statement - with any changes to Project Success Plan Section 1.
-
Document Pre-Configure and Deployment Requirements.
-
Document configure and Deployment Assumptions.
-
Document Configure and Deployment Resource Plan.
-
Document Configure and Deployment Detailed Plan.
-
Training Plan
-
Support Plan
-
Acceptance Test Plan
-
Design Documents
|
Key Considerations
Inputs
-
Identified, mobilized, and oriented project team
-
Project Success Plan Section 1
Outputs
-
Project Success Plan Sections 1 and 2 document
|
Licensed Materials - Property of IBM. (c) Copyright IBM Corp. 2005,
2015. IBM and the IBM logo are trademarks of International Business Machines Corp, registered in many
jurisdictions worldwide. Other products and service names may be trademarks of IBM or other companies. You
may use the Content 'AS IS" or modify them, however IBM will not be responsible for any deficiencies or
errors that result from modifications that you make.
|
|
|